Closes HJ-357, HJ-155

Description Of Changes

• Updates functionality of Custom Report reset to reset the entire table to its default state once applied, not just reset the filter.
• Restores the Filter accordion label
• Fixes ordering to be based on the tableinstance columns, rather than the backend defined columns.
• Enhances Cypress tests to help catch these issues in the future

Steps to Confirm

1. Clear Local Storage for AdminUI or open an ingocnito window. Log in again.
2. Assuming you have systems set up in your Admin UI, visit the Datamap Report page /reporting/datamap.
3. Add a filter to the report using the Filters dialog. While doing that, note that all 3 accordions have labels (the top one was missing).
4. Update the grouping of the report. Note that the only column order change when doing so are the first 2 columns (the rest were being reordered unintentionally)
5. Change various other aspects of the table (column order, column naming, column visibility) and save as a custom report using the reports dropdown.
6. Reload the page, ensuring that the custom report is still applied.
7. Open the custom report dropdown again and click "reset" then "Apply"
8. The table should now be back to default state. Reloading the page should retain this default state.

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
• Followup issues:
  • Followup issues created (include link)
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required